The Cisco PE router providing MPLS Layer 2 Virtual Private Network (L2VPN) services must be configured to authenticate targeted Label Distribution Protocol (LDP) sessions used to exchange virtual circuit (VC) information using a FIPS-approved message authentication code algorithm.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-216794	CISC-RT-000660	SV-216794r531087_rule		Medium

Description
LDP provides the signaling required for setting up and tearing down pseudowires (virtual circuits used to transport Layer 2 frames) across an MPLS IP core network. Using a targeted LDP session, each PE router advertises a virtual circuit label mapping that is used as part of the label stack imposed on the frames by the ingress PE router during packet forwarding. Authentication provides protection against spoofed TCP segments that can be introduced into the LDP sessions.

Description

LDP provides the signaling required for setting up and tearing down pseudowires (virtual circuits used to transport Layer 2 frames) across an MPLS IP core network. Using a targeted LDP session, each PE router advertises a virtual circuit label mapping that is used as part of the label stack imposed on the frames by the ingress PE router during packet forwarding. Authentication provides protection against spoofed TCP segments that can be introduced into the LDP sessions.

STIG	Date
Cisco IOS XR Router RTR Security Technical Implementation Guide	2020-09-23

Details

Check Text ( C-18026r507365_chk )
The Cisco router is not compliant with this requirement; hence, it is a finding. However, the severity level can be downgraded to a category 3 if the router is configured to authenticate targeted LDP sessions using MD5 as shown in the configuration example below. mpls ldp router-id 10.1.1.2 neighbor 10.1.1.1 password encrypted xxxxxxxxxxxxxxx neighbor 10.1.2.1 password encrypted xxxxxxxxxxxxxxx If the router is not configured to authenticate targeted LDP sessions using MD5, the finding will remain as a CAT II.

Check Text ( C-18026r507365_chk )

The Cisco router is not compliant with this requirement; hence, it is a finding. However, the severity level can be downgraded to a category 3 if the router is configured to authenticate targeted LDP sessions using MD5 as shown in the configuration example below.

mpls ldp
router-id 10.1.1.2
neighbor 10.1.1.1
password encrypted xxxxxxxxxxxxxxx
neighbor 10.1.2.1
password encrypted xxxxxxxxxxxxxxx

If the router is not configured to authenticate targeted LDP sessions using MD5, the finding will remain as a CAT II.

Fix Text (F-18024r507366_fix)
The severity level can be downgraded to a category 3 if the router is configured to authenticate targeted LDP sessions using MD5 as shown in the example below. RP/0/0/CPU0:R3(config)#mpls ldp RP/0/0/CPU0:R3(config-ldp)#neighbor 10.1.1.1 RP/0/0/CPU0:R3(config-ldp)#neighbor password clear xxxxxxxx RP/0/0/CPU0:R3(config-ldp)#neighbor 10.1.2.1 RP/0/0/CPU0:R3(config-ldp)#neighbor password clear xxxxxxxx RP/0/0/CPU0:R3(config-ldp)#commit

Fix Text (F-18024r507366_fix)

The severity level can be downgraded to a category 3 if the router is configured to authenticate targeted LDP sessions using MD5 as shown in the example below.

RP/0/0/CPU0:R3(config)#mpls ldp
RP/0/0/CPU0:R3(config-ldp)#neighbor 10.1.1.1
RP/0/0/CPU0:R3(config-ldp)#neighbor password clear xxxxxxxx
RP/0/0/CPU0:R3(config-ldp)#neighbor 10.1.2.1
RP/0/0/CPU0:R3(config-ldp)#neighbor password clear xxxxxxxx
RP/0/0/CPU0:R3(config-ldp)#commit